Skip to content

[Snyk] Security upgrade astro from 5.3.0 to 6.0.0#590

Open
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-8f25d5b19028ec94cf61650fcb37dddf
Open

[Snyk] Security upgrade astro from 5.3.0 to 6.0.0#590
snyk-io[bot] wants to merge 1 commit intomasterfrom
snyk-fix-8f25d5b19028ec94cf61650fcb37dddf

Conversation

@snyk-io
Copy link
Copy Markdown

@snyk-io snyk-io bot commented Mar 26, 2026

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • docs/package.json
  • docs/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-ASTRO-15763371
  227  
medium severity Directory Traversal
SNYK-JS-ASTROJSINTERNALHELPERS-15763364
  62  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling
🦉 Directory Traversal

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Mar 26, 2026

Merge Risk: High

This is a major version upgrade from Astro v5 to v6 that introduces significant breaking changes, requiring code and environment updates.

Key Breaking Changes:

  • Node.js Requirement: Support for Node.js versions 18 and 20 has been dropped. Your environment must be updated to Node.js 22 or later.
  • API Removals: Several deprecated APIs and features have been removed, including:
    • Astro.glob()
    • Legacy Content Collections support (projects must use the Content Layer API introduced in v5).
    • The deprecated <ViewTransitions /> component.
  • Dependency Upgrades: Core dependencies have been upgraded, which may require changes:
    • Zod 4: Astro now uses Zod 4 for schema validation. You must update imports from astro:content to astro/zod. This version has its own breaking changes in validation methods.
    • Vite 7: If your project has a pinned Vite version, it must be updated to v7 or later.
  • Cloudflare Adapter: Users of the @astrojs/cloudflare adapter will need to update their configuration for v13, as options like platformProxy have been removed and entrypoints have changed.

Recommendation: Due to the number of breaking changes, a careful review of the official migration guide is required. The upgrade will likely involve refactoring content collections, updating environment versions, and changing API usage.

Source: Astro v6 Migration Guide

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@snyk-io
Copy link
Copy Markdown
Author

snyk-io bot commented Mar 26, 2026

Snyk checks have failed. 2 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (2)
Open Source Security 0 0 0 0 0 issues
Licenses 0 2 0 0 2 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants